Systems and methods for creating software from library and custom components

ABSTRACT

Methods and systems are disclosed that automate and institutionalize many aspects of the process of creating software. Embodiments automate aspects of pricing, software creation, and delivery using a manufacturing-styled approach to development that reuses existing code and other existing software design features.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Application is a Continuation of application Ser. No. 17/380,456 filed on Jul. 20, 2021. Application Ser. No. 17/380,456 is a Continuation of application Ser. No. 16/854,805 filed on Apr. 21, 2020. Application Ser. No. 16/854,805 is a Continuation of application Ser. No. 15/786,431 filed on Oct. 17, 2017. Application Ser. No. 15/786,431 claims the benefit of U.S. Provisional Application 62/408,935 filed on Oct. 17, 2016. The entire contents of these applications are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The claimed subject matter relates to the field of software, and more particularly to the creation of software from library components and custom components.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows a simplified block diagram of an embodiment of a system for creating software;

FIG. 2 shows a more detailed diagram of an example of a computing device from a system for creating software;

FIG. 3 is a simplified block diagram of an embodiment of a system for creating software;

FIG. 4 is a diagram showing a block diagram of aspects of system architecture of an embodiment for creating software, i.e., decision triggers and user flow, and a block diagram illustrating back end components of an embodiment for creating software;

FIGS. 5-10 describe and illustrate aspects of the problem and the solution to the problem provided by embodiments of the systems and methods;

FIGS. 11-12 describe and illustrate aspects of how the user acquires access to embodiments and aspects of the value provided by embodiments of the systems and methods;

FIG. 13 is a block diagram illustrating an overview of an embodiment for creating software;

FIG. 14 is a block diagram illustrating a project scope and pricing process of an embodiment for creating software;

FIG. 15 is a block diagram illustrating a code selection and integration process of an embodiment for creating software;

FIG. 16 is a block diagram illustrating a project development process of an embodiment for creating software;

FIG. 17 is a block diagram illustrating a customer relationship and management process of an embodiment for creating software;

FIGS. 18-37 describe and illustrate a user experience and flow using screenshots from a user interface of an embodiment for creating software; and

FIGS. 38-43 describe and illustrate an administrative user interface and flow using screenshots of an embodiment for creating software.

DETAILED DESCRIPTION

FIG. 1 is a simplified block diagram of a distributed computer network 100 incorporating an embodiment of the present invention. Computer network 100 includes a number of client systems 105, 110, and 115, and a server system 120 coupled to a communication network 125 via a plurality of communication links 130. Communication network 125 provides a mechanism for allowing the various components of distributed network 100 to communicate and exchange information with each other.

Communication network 125 may itself be comprised of many interconnected computer systems and communication links. Communication links 130 may be hardwire links, optical links, satellite or other wireless communications links, wave propagation links, or any other mechanisms for communication of information. Various communication protocols may be used to facilitate communication between the various systems shown in FIG. 1 . These communication protocols may include TCP/IP, HTTP protocols, wireless application protocol (WAP), vendor-specific protocols, customized protocols, and others. While in one embodiment, communication network 125 is the Internet, in other embodiments, communication network 125 may be any suitable communication network including a local area network (LAN), a wide area network (WAN), a wireless network, a intranet, a private network, a public network, a switched network, Internet telephony. IP telephony, digital voice, voice over broadband (VoBB), broadband telephony, Voice over IP (VoIP), public switched telephone network (PSTN), and combinations of these, and the like.

System 100 in FIG. 1 is merely illustrative of an embodiment and does not limit the scope of the systems and methods as recited in the claims. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. For example, more than one server system 120 may be connected to communication network 125. As another example, a number of client systems 105, 110, and 115 may be coupled to communication network 125 via an access provider (not shown) or via some other server system. An instance of a server system 120 and a computing device 105 may be part of the same or a different hardware system. An instance of a server system 120 may be operated by a provider different from an organization operating an embodiment of a system for specifying an object in a design, or may be operated by the same organization operating an embodiment of a system for specifying an object in a design.

Client systems 105, 110, and 115 typically request information from a server system which provides the information. Server systems by definition typically have more computing and storage capacity than client systems. However, a particular computer system may act as both a client and a server depending on whether the computer system is requesting or providing information. Aspects of the system may be embodied using a client-server environment or a cloud-cloud computing environment.

Server 120 is responsible for receiving information requests from client systems 105, 110, and 115, performing processing required to satisfy the requests, and for forwarding the results corresponding to the requests back to the requesting client system. The processing required to satisfy the request may be performed by server system 120 or may alternatively be delegated to other servers connected to communication network 125.

Client systems 105, 110, and 115 enable users to access and query information or applications stored by server system 120. Some example client systems include portable electronic devices (e.g., mobile communication devices) such as the Apple iPhone®, the Apple iPad®, the Palm Pre™, or any device running the Apple iOS™, Android™ OS, Google Chrome OS, Symbian OS®, Windows Mobile® OS, Palm OS® or Palm Web OS™. In a specific embodiment, a “web browser” application executing on a client system enables users to select, access, retrieve, or query information and/or applications stored by server system 120. Examples of web browsers include the Android browser provided by Google, the Safari® browser provided by Apple, the Opera Web browser provided by Opera Software, the BlackBerry® browser provided by Research In Motion, the Internet Explorer® and Internet Explorer Mobile browsers provided by Microsoft Corporation, the Firefox® and Firefox for Mobile browsers provided by Mozilla®, and others.

FIG. 2 shows an exemplary computer system such as a client system of the present invention. In an embodiment, a user interfaces with the system through a client system, such as shown in FIG. 2 . Mobile client communication or portable electronic device 200 includes a display, screen, or monitor 205, housing 210, and input device 215. Housing 210 houses familiar computer components, some of which are not shown, such as a processor 220, memory 225, battery 230, speaker, transceiver, antenna 235, microphone, ports, jacks, connectors, camera, input/output (I/O) controller, display adapter, network interface, mass storage devices 240, and the like. Computer system 200 may include a bus or other communication mechanism for communicating information between components. Mass storage devices 240 may store a user application and system software components. Memory 225 may store information and instructions to be executed by processor 220.

Input device 215 may also include a touchscreen (e.g., resistive, surface acoustic wave, capacitive sensing, infrared, optical imaging, dispersive signal, or acoustic pulse recognition), keyboard (e.g., electronic keyboard or physical keyboard), buttons, switches, stylus, gestural interface (contact or non-contact gestures), biometric input sensors, or combinations of these.

Mass storage devices 240 may include flash and other nonvolatile solid-state storage or solid-state drive (SSD), such as a flash drive, flash memory, or USB flash drive. Other examples of mass storage include mass disk drives, floppy disks, magnetic disks, optical disks, magneto-optical disks, fixed disks, hard disks, CD-ROMs, recordable CDs, DVDs, recordable DVDs (e.g., DVD-R, DVD+R, DVD-RW, DVD+RW, HD-DVD, or Blu-ray Disc), battery-backed-up volatile memory, tape storage, reader, and other similar media, and combinations of these.

System 100 may also be used with computer systems having different configurations, e.g., with additional or fewer subsystems. For example, a computer system could include more than one processor (i.e., a multiprocessor system, which may permit parallel processing of information) or a system may include a cache memory. The computer system shown in FIG. 2 is but an example of a computer system suitable for use. Other configurations of subsystems suitable for use will be readily apparent to one of ordinary skill in the art. For example, in a specific implementation, the computing device is mobile communication device such as a smartphone or tablet computer. Some specific examples of smartphones include the Droid Incredible and Google Nexus One®, provided by HTC Corporation, the iPhone® or iPad®, both provided by Apple, BlackBerry Z10 provided by BlackBerry (formerly Research In Motion), and many others. The computing device may be a laptop or a netbook. In another specific implementation, the computing device is a non-portable computing device such as a desktop computer or workstation.

A computer-implemented or computer-executable version of the program instructions useful to practice the present invention may be embodied using, stored on, or associated with computer-readable medium. A computer-readable medium may include any medium that participates in providing instructions to one or more processors for execution. Such a medium may take many forms including, but not limited to, nonvolatile, volatile, and transmission media. Nonvolatile media includes, for example, flash memory, or optical or magnetic disks. Volatile media includes static or dynamic memory, such as cache memory or RAM. Transmission media includes coaxial cables, copper wire, fiber optic lines, and wires arranged in a bus. Transmission media can also take the form of electromagnetic, radio frequency, acoustic, or light waves, such as those generated during radio wave and infrared data communications.

For example, a binary, machine-executable version, of the software useful to practice the present invention may be stored or reside in RAM or cache memory, or on mass storage device 240. The source code of this software may also be stored or reside on mass storage device 240 (e.g., flash drive, hard disk, magnetic disk, tape, or CD-ROM). As a further example, code useful for practicing the invention may be transmitted via wires, radio waves, or through a network such as the Internet. In another specific embodiment, a computer program product including a variety of software program code to implement features of the invention is provided.

Computer software products may be written in any of various suitable programming languages, such as C, C++, C#, Pascal, Fortran, Perl, Matlab (from MathWorks, www.mathworks.com), SAS, SPSS, JavaScript, CoffeeScript, Objective-C, Objective-J, Ruby, Python, Erlang, Lisp, Scala, Clojure, and Java. The computer software product may be an independent application with data input and data display modules. Alternatively, the computer software products may be classes that may be instantiated as distributed objects. The computer software products may also be component software such as Java Beans (from Oracle) or Enterprise Java Beans (EJB from Oracle).

An operating system for the system may be the Android operating system, iPhone OS (i.e., iOS), Symbian, BlackBerry OS, Palm web OS, bada, MeeGo, Maemo, Limo, or Brew OS. Other examples of operating systems include one of the Microsoft Windows family of operating systems (e.g., Windows 95, 98, Me, Windows NT, Windows 2000, Windows XP, Windows XP x64 Edition, Windows Vista, Windows 7, Windows CE, Windows Mobile, Windows Phone 7), Linux, HP-UX, UNIX, Sun OS, Solaris, Mac OS X, Alpha OS, AIX, IRIX32, or IRIX64. Other operating systems may be used.

Furthermore, the computer may be connected to a network and may interface to other computers using this network. The network may be an intranet, internet, or the Internet, among others. The network may be a wired network (e.g., using copper), telephone network, packet network, an optical network (e.g., using optical fiber), or a wireless network, or any combination of these. For example, data and other information may be passed between the computer and components (or steps) of a system useful in practicing the invention using a wireless network employing a protocol such as Wi-Fi (IEEE standards 802.11, 802.11a, 802.11b, 802.11e, 802.11g, 802.11i, and 802.11n, just to name a few examples). For example, signals from a computer may be transferred, at least in part, wirelessly to components or other computers.

FIG. 3 is a simplified block diagram of an embodiment of a system 300 for creating software for use by a user 301. System 300 includes one or more user computing devices 305, and a server 320, coupled to a communication network 325 via a plurality of communication links 330. Computing device 305 may be used to run a user application 310 for creating software from existing code and new code. User application 310 may use computing device 305 and network 325 to access server 320. Communication network 325 (or “network 325”) provides a mechanism for allowing the various components of system 300 to communicate and exchange information with each other via communication links 330. Server 320 may include or have access to a database 340 of code libraries 342 a, 342 b, . . . , 342 n. Each code library includes software code (not shown) from which system 300 may select to create customized software. Each code library 342 a, 342 b, . . . , 342 n may have selected from it a subset of code sections 345 a, 345 b, . . . , 345 n, which server 320 may assemble into customized software 350 a, 350 b, . . . , 350 n and provide to user 301 via computing device 305. Customized software may be complete or may need to be augmented with additional custom code sections that may be newly created by partner developers. Server 320 or an administrator may combine or integrate newly created code with existing code sections to create customized software.

Computing device 305 may run a software-creating component 315 which may be provided with a subset of code sections (e.g., subset 345 a from server 320 via user application 310) that software-creating component 315 (like server 320) may assemble into customized software (e.g., customized software 350 a).

Network 325 may be any suitable communications network. Communication network 325 may itself be comprised of many interconnected computer systems and communication links. As an example and not by way of limitation, one or more portions of network 325 may include an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular telephone network, another suitable network, or a combination of two or more of these. Network 325 may include one or more networks 325.

Connections 330 may connect computing device 305 and server 320 to communication network 325 or to each other. Communication links 330 may be hardwire links, optical links, satellite or other wireless communications links, wave propagation links, or any other mechanisms for communication of information. This disclosure contemplates any suitable connections 325. In particular embodiments, one or more connections 325 include one or more wireline (such as for example Digital Subscriber Line (DSL) or Data Over Cable Service Interface Specification (DOCSIS)), wireless (such as for example Wi-Fi or Worldwide Interoperability for Microwave Access (WiMAX)) or optical (such as for example Synchronous Optical Network (SONET) or Synchronous Digital Hierarchy (SDH)) connections. In particular embodiments, one or more connections 330 each include an ad hoc network, an intranet, an extranet, a VPN, a LAN, a WLAN, a WAN, a WWAN, a MAN, a portion of the Internet, a portion of the PSTN, a cellular telephone network, another suitable connection 330, or a combination of two or more such connections 330. Connections 330 need not necessarily be the same throughout system 300. One or more first connections 330 may differ in one or more respects from one or more second connections 330.

Server 320 may be a network-addressable computing system that can host one or more product databases 340. Server 320 may be responsible for receiving information requests from computing device 305 via user application 310, for performing the processing required to satisfy the requests, for generating responses (e.g., custom software 350 a, . . . , 350 n) to received inquiries, and for forwarding the results corresponding to the requests back to requesting computing device 305. Server 320 may store, receive, or transmit data and software, and information associated with the data and software (including user data). The processing required to satisfy the requests may be performed by server 320 or may alternatively be delegated to other servers connected to communication network 325. For example, other servers may host database 340, or have additional databases. Server 320 may be an intermediary in communications between a computing device 305 and another server system, or a computing device 305 may communicate directly with another server system. Server 320 may be accessed by the other components of system 300, for example, directly or via network 325. In particular embodiments, one or more users 301 may use one or more computer devices 305 to access, send data to, and receive data from server 320.

Computing device 305, connections 330, and network 325, enable user 301 to access and query information stored and applications run by server 320, such as database 340. Some example computer devices 305 include desktop computers, portable electronic devices (e.g., mobile communication devices, smartphones, tablet computers, laptops) such as the Samsung Galaxy Tab®, Google Nexus devices, Amazon Kindle®, Kindle Fire®, Apple iPhone®, the Apple iPad®, Microsoft Surface®, the Palm Pre™, or any device running the Apple iOS®, Android® OS, Google Chrome® OS, Symbian OS®, Windows Mobile® OS, Windows Phone, BlackBerry® OS, Embedded Linux, Tizen, Sailfish, webOS, Palm OS® or Palm Web OS®.

In an embodiment, user application 310 may be run or executed by a different system. For example, computing device 305, or server 320, or both, may run user application 310. That is, user application 310 may be run by computing device 305, or the application may be run on server 320 and accessed by computing device 305 through a browser and network 325. For example, computing device 305 could be operated as a terminal, with user application 310 being run on a server, e.g., server 320. In an embodiment, aspects or functionalities of user application 310 are run by server 320, or another computing system or server. In an embodiment, the steps of the methods described herein may be performed, at least in part, in cloud-computing environment.

FIG. 3 illustrates a particular arrangement of user 301, computing device 305, and server 320, but this is an example arrangement. Any other suitable arrangement of user 301, computing device 305, server 320, and network 325 may be used. For example, computing device 305 may be connected directly to server 320. Also, computing device 305 and server 320 may appear to be distinct yet operate on the same hardware. In addition, any number of users 301, clients 305, and server 320 may be used in embodiments.

FIG. 4 is a diagram showing block diagrams of system architecture of an embodiment for creating software.

In an embodiment, a method for creating software is called “Engineer.ai.”

Why was Engineer.ai created? Engineer.ai was created to allow for the building of digital products at least 30% faster and for 30% less than anyone else in the industry, all while guaranteeing top quality.

What is it and how does it work? Engineer.ai is an “as-a-service” platform for software outsourcing, turning App Development/Software Outsourcing into something as simple as a restaurant menu that you can pick a-la carte. This includes an On-Demand & Online Price Calculator for building any digital product from a Wearable to a Marketplace to an App with price guarantees, and intelligent automation/machine assistance that reduces the average cost and time of any project by at least 30%-40%. Engineer.ai offers a transparent fixed price upfront. No surprises and any amount over your fixed price is waived.

How does the service/product work? Engineer.ai provides an intuitive and easy-to-use wizard for pricing any idea in less than 60 seconds with pre-set options made available based on the project type. The fixed price you get is offered immediately and upfront. You don't need to wait or speak to a salesperson to know exactly what your project will cost and how long it will take to deliver.

How is my project managed? Engineer.ai provides weekly updates so you always know the exact status of your project. Engineer.ai practices gold standard for coding so quality is never sacrificed. Engineer.ai offers a weekly subscription and billing model so you are never locked in and can pause, speed up, or walk away at anytime.

Engineer.ai Benefits

-   1) Build your idea for 30% less and 30% faster than your     competitors. -   2) Use our easy-to-use wizard for pricing any idea in less than 60     seconds. -   3) Get transparent and fixed pricing for your project upfront and     instantaneously without speaking to a sales rep. -   4) Have the confidence your project will be delivered on time and     will not go over budget. -   5) If you are not sure what you want, use our wizard to build out     your idea by choosing from a bundle of pre-set options.

Engineer.ai Description

Engineer.ai uses machines to automate and institutionalize as much of the software outsourcing process as possible. Engineer.ai includes transparent pricing, standardized delivery, and a manufacturing-styled approach to development that reuses an estimated 50% of code and design that is often standardized and duplicated across many apps and digital platforms.

A key part of our business model is how Engineer.ai actually scales and builds. Engineer.ai scales by using 3rd party dev shops/contractors and having them deliver under the Engineer.ai brand, and Engineer.ai uses code libraries. Similarly Engineer.ai lets Software Companies get predictable revenue, a framework that lets them get paid and a way for them to access our rich code libraries & SIMBA Platform (Simple, Integrated, Machine-Based, Architecture Platform). Engineer.ai also scales by the institutionalization of the Engineer.ai code and development process.

SIMBA connects the entire product delivery process together. It integrates on-boarding, pricing, engineering and product/project management using machine-learning processing and A.I. (“artificial intelligence”) to keep constant conversation with the customer. Aspects of SIMBA include:

-   -   A “Pick-n-mix” wizard for pricing any idea.     -   A weekly subscription with max price guarantee.     -   A learning algorithm for real-time pricing.     -   A machine-created templates from code library for efficient &         consistent delivery.     -   And an automated project and progress reports to ensure that         customers have transparency in pricing, financial control, and         automation

Engineer.ai is the first service to unify Development Shops around the world:

-   -   First published pricing platform that lets your price an app or         an idea within 30 seconds online.     -   First process-driven and machine-led manufacturing approach for         building software in a “just-in-time” model.     -   First use of machine-learning and Artificial Intelligence in         machines and BOTs (software applications that run automated         tasks (scripts) over the Internet) to automate the product         delivery process.     -   For areas Engineer.ai feels need more “business interest,”         Engineer.ai may subsidize the development, such as efforts with         content-led marketplaces; Engineer.ai can effectively invest in         customers by simply offsetting some of its fees.

Role of SIMBA in Engineering.ai:

-   -   Automated Pricing     -   Machine-assisted product management     -   Code creation

Engineer.ai—Features

-   1) Project selector     -   a) Category selection         -   i) Current categories         -   ii) Option for more categories         -   iii) Metrics to track selection and % completion     -   b) Template type     -   c) Other project description (outside selector parameters)     -   d) Platforms     -   e) Feature preview     -   f) Portfolio examples     -   g) Team location     -   h) Dev speed (time to market)     -   i) Build fidelity -   2) Pricing estimate     -   a) Real time projected cost based on project guidelines created         in the selector -   3) Customer contact capture & confirmation     -   a) Project review (can user adjust here?)     -   b) Customer contact collected     -   c) Saved confirmation of submission via email

Engineer.ai—Additional Features

-   1) Project estimator additional features     -   a) Wireframe database     -   b) Intelligence re: additional categories & dataset     -   c) Mobile & touch friendly     -   d) Workflow for customer/sales interaction     -   e) In an embodiment, the method makes a decision based on         historical variance. For example, if there is some customization         required for a particular type of app, and if the type of app         shows a historical cost variation, the method adjusts the         potential customization cost based on the historical variation. -   2) Payment & contract execution     -   a) Proposal automation         -   i) Proposal based on integration (the degree and depth of             integration)     -   b) Billed deposit and weekly, monthly invoice     -   c) Pay from invoice -   3) Design     -   a) Goal to assign to the right designer     -   b) Preview based on component elements & wireframes     -   c) Map to design library     -   d) 2-3 week iteration with customer (details?) -   4) Project team assignment     -   a) Semi-automated     -   b) Track team member status & availability projection -   5) Component user story generation     -   a) Board creation     -   b) Database of tagged stories     -   c) Feature based story selection -   6) Base code generation     -   a) Code pods     -   b) Feature based pod selection -   7) Sprint estimator     -   a) Feature/team/speed based estimation of completion     -   b) Automated notifications of progress, potential deadline         extensions, and sprint completions

Engineer.ai—Partner Development Qualification Process

-   1) Sources     -   a) Inbound         -   i) Website     -   b) Outbound     -   c) Referral -   2) Pre-qualification     -   a) Minimum team requirements     -   b) Ideal candidate profile—measure fill rate success/skills,         experience, etc     -   c) Team profiling tool         -   i) Team members         -   ii) Skills (dev lang, years experience, code committed)         -   iii) Projects (associated projects) -   3) Project review     -   a) Minimum project examples—Live products ideal     -   b) Customer testimonials -   4) Code review     -   a) Standardized code submission     -   b) Submission, automated and manual review, and workflow process

TABLE 1 gives a description of pages from a website employing embodiments of a method for creating software from library and custom components. In TABLE 1, a particular webpage is identified by the columns: ID, Title, and Labels. A Description column includes a description of the particular webpage and its function.

ID TITLE LABELS DESCRIPTION 129382929 Product homepage As a user when I navigate to Engineer.ai's URL, I will Homepage/ be navigated to landing page of Engineer.ai. Landing The Landing page will present 5 Main Card options Page to choose from. 1. Mobile App 2. Blog/Website 3. Marketplace 4. Wearables 5. Others **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 18 for design reference. 129383567 Homepage | homepage As a user, when I hover on the cards on the landing Card Hover page, then the Main card will move up and an overlay State card will reveal options related to the main card. I should also see two buttons - **Start** and **Know More**. **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 19 for design reference. 129446881 Homepage | homepage As a user, when I click on *Know more* button after Card Hover hovering on a card, there should be another overlay State | over the same card revealing the full feature set that Know More are applicable for card being hovered upon. The feature set list can be longer than the display area and thus needs to be horizontally scrollable. A start button will also appear below the feature list. I can click on *Start* button and should be able to follow story #129446683 There will be another button under start by the name of *Portfolio Projects*. Clicking on it will work as described in story #129447399 **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 20 for design reference. 129440667 Personalize personalize As a user, when I am navigated to this screen through Product | product the workflow defined in story #129521135, I should Select see the first section to select the platforms I need to Platform support in my Product. This is the first step towards personalization of my product. Below the applicable platforms list, I should be able to see the number of screens anticipated in my product. A **Next** button appears below, clicking on which I should be able to follow story #129514959. This button gets enabled only when I have one or more options from all required fields selected in this section. **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 27 for design reference. 129515019 Personalize personalize As a user, when I am navigated to this screen through Product | product the workflow defined in story #129514959 (on click Select on next), the third section overlay should come to top. Delivery This will allow me to select the team I want to use to Speed develop my product and is the third step towards personalization of my product. A back button will appear below to the header clicking on which I will be navigated to Select Features story (#129514959) A **Next** button appears below, clicking on which I should be able to follow story #129515169. This button gets enabled only when I have one or more options from all required fields selected in this section. **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 28 for design reference. 129515169 Personalize personalize As a user, when I am navigated to this screen through Product | product the workflow defined in story #129515019 (on click Select on next), the third section overlay should come to top. Delivery This will allow me to select the speed of delivery for Speed my product and is the fourth step towards personalization of my product. A back button will appear below to the header clicking on which I will be navigated to Select Features story (#129515019) A **Next** button appears below, clicking on which I should be able to follow story #129522065. This button gets enabled only when I have one or more options from all required fields selected in this section. **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 30 for design reference. 129514959 Personalize personalize As a user, when I am navigated to this screen through Product | product the workflow defined in story #129440667 (on click Select on next), the second section overlay should come to Features top. This will allow me to select the features I need to include in my Product and is the second step towards personalization of my product. A **Back Button** will appear below to the header clicking on which I will be navigated to Select Platform & Pages story (#129440667) A **Next** button appears below, clicking on which I should be able to follow story #129515019. This button gets enabled only when I have one or more options from all required fields selected in this section. **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 36 for design reference. 129446683 Product homepage, As a user, when I click on *Start* button from hover Type product state or additional card overlays, I should be Landing type navigated to a separate page which will show cards Page (Start based on the card selected on homepage. from any Additionally, if I click on header section of this card, card on the same workflow should be followed. Homepage) **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 35 for design reference. 129514073 Product product As a user, when I hover on a card in Product Type Type Page | type page, the card should show the list of platforms that Card Hover are applicable for that product type. State A *Know more* button will also appear below the applicable platforms list. I can click on this button and should be able to follow story #129514203 On clicking the header of this card, I should be able to follow story #129514387 **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 26 for design reference. 129522743 Personalize personalize As a user, when I am navigated to this screen through Product | product the workflow defined in story #129522065 (on click Your Build on next), the build card should appear. This screen Card shows your selections through 4 cards as showcased in the design reference. It should display the following 4 cards in the given order: * Product Type with description * Platform, Screens and Features list * Team and Speed * Development Phases and Estimate A **Get in Touch** button appears inside the 4th card, clicking on which I should be able to follow story #129522917. **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend, unless stated otherwise. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 33 for design reference. 129522065 Personalize personalize As a user, when I am navigated to this screen through Product | product the workflow defined in story #129515169 (on click Select on next), the phase selection screen should appear. It Project is the final step towards personalization of my Phases product and product development lifecycle. It should display the following 4 phases: * Design * Prototype * MVP * Full Build By default all the 4 phases will be selected. As a user, I should also be able to unselect the selected card(s) as many times and vice-versa. The estimate in header should update instantly based on the selections I am making. A **Next** button appears below, clicking on which I should be able to follow story #129522743. This button gets enabled only when I have one or more options from all required fields selected in this section. **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend, unless stated otherwise. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 32 for design reference. 129514203 Product product As a user, when I click on *Next* button on hovered Type Page | type card in Products page, I should be able to see the Card Hover features I can request for. The card overlay that State | opened in previous view moves a bit up to Know More accommodate the list. If the list requires more space than available in the display area, the list should be horizontally paginated. A *Next* button will also appear below the applicable features list. I can click on this button and should be able to follow story **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 20 for design reference. 129757983 Add in Depending on what the user selects, the price should pricing constantly be updating in the top-right section of the component navbar 129521135 Create the personalize As a user, when I am navigated to this screen through Personalize product the workflow defined in story #129514387, I should Product see a card that has 4 dynamic sections stacked over Page one another. These sections (in defined order) are * Select Platforms *(Hard Coded Label)* * Select Features *(Hard Coded Label)* * Select Team *(Hard Coded Label)* * Select Speed *(Hard Coded Label)* Initially, only the first section will be enabled and rest will be disabled. As and when I keep selecting options in each section, the next section in stack gets enabled. I can also navigate directly between all the enabled sections directly by clicking them. The selected sections comes on top while others are visible in the background. For linear navigation between enabled sections, I should also be able to use the Back and Next button in each sections. The first section should not have a back button. **Note:** The most of the text in sections like title, description etc. along with icons is **not hardcoded** and is available through backend; unless stated otherwise. See, e.g., the screenshot on FIG. 27. 129522917 Personalize personalize As a user, when I am navigated to this screen through Product | product the workflow defined in story #129522743 (on click Get in on “Get in Touch” button), the Get in Touch screen Touch should appear. This screen should allow me to enter Screen information in following fields: * Project Name (100 Characters) * Project Description (150 Characters) * My email ID (75 Characters) * My Name (50 Characters) Below these fields, there should be a checkbox asking me to confirm that I agree to *Terms & Conditions* and *Privacy Policy* I can also request for a *“Non Disclosure Agreement”* through another link below the above checkbox. Lastly, I should be able to save the details and allow the team to connect with me. I should now be navigated to next screen which follows story #129523531. See, e.g., the screenshot on FIG. 34 for design reference. 129525811 Show and As a user I would like to see a dynamic header in the update application. This header is visible when I click on Header Start on any of the main cards on the home screen. The header has 5 sections (Collapsed form) The header has 5 sections (Expanded form) * Product Type * Product Sub Type & Its description * Platform, Features, Team and Speed * Phase * Estimate Each section/sub-section will be added to header as and when user navigates to these pages/sections and makes necessary selections on screen. Any update in these sections also instantly update the header with new information. I can also click on Header to see the expanded view. Please see the below design for reference for collapsed view See, e.g., the screenshot on FIG. 35 for design reference. 129514387 Product product As a user, when I click on *Next* button on hovered Type Page | type card in Products page, an overlay will stack over Add product existing overlays and allow me to add a description description about the kind of product that I want to build. The description cannot be longer than 50 characters. Alternately, I can reach here by clicking the card header on *Product Types* page at any point of time. A *Start* button appear below the text field. I can click on this button and should be able to follow story #129440667 **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references. See, e.g., the screenshot on FIG. 37 for design reference. 129523531 Create the personalize As a user, when I am navigated to this screen through Concierge product the workflow defined in story #129522917 (on click page on “Get in Touch” button), the Concierge screen should appear. Here, I should be able to post my queries and add attachments. **Attachment types TBD**. Lastly, I should be able to start an estimation for a new build which redirects me to homepage. 129447399 Homepage | homepage, As a user, when I click on *Portfolio Projects* button Card Hover skip in know more section of a card on Home page, a new State | overlay will appear as showcased in the design Know More | reference. Portfolio It should show a list of 4 customers and a few testimonials. The testimonials should be horizontally scrollable. A start button will also appear below the feature list. I can click on *Start* button and should be able to follow story #129446683 **Note:** The entire text on cards like title, description etc. along with icons is **not hardcoded** and is available through backend. Please ignore text on all cards in the design references.

In the description above and throughout, numerous specific details are set forth in order to provide a thorough understanding of an embodiment of this disclosure. It will be evident, however, to one of ordinary skill in the art, that an embodiment may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form to facilitate explanation. The description of the preferred embodiments is not intended to limit the scope of the claims appended hereto. Further, in the methods disclosed herein, various steps are disclosed illustrating some of the functions of an embodiment. These steps are merely examples, and are not meant to be limiting in any way. Other steps and functions may be contemplated without departing from this disclosure or the scope of an embodiment.

Systems and methods are described for creating software from library and custom components. In a method for creating software, a server running a software creating component may receive input from a customer, where the input describes at least one aspect of a software program. Based on the input, the software creating component may determine existing code components that may be used to create the software program, where the existing code components are stored in a code library accessible by the software creating component. Based on the user input and based on the existing code components that may be used to create the software program, the software creating component may determine new code components that must be developed for the software program. And, based on the existing code components that may be used and based on the new code components that must be developed, the software creating component may provide, to the user, a cost estimate for the software program.

Different embodiments may provide variations on the basic principles outlined above. In an embodiment, the method may further comprise adjusting the cost estimate based on the at least one aspect of the software program. In an embodiment, the at least one aspect of the software program may include at least one of: a platform category, an application template, a requirement collection, a platform, a number of screens, a feature, a team location, a time to market, and a build depth. In an embodiment, the build depth may include: a wireframe, a design, a navigable prototype, a minimal viable product, or a complete project. In an embodiment, the method may further comprise: sending, by the software creating program, a set of existing code requirement and a set of new code requirements to a team selector; and generating, by the software creating program, a project template based on the existing code components that may be used and based on the new code components that must be developed. In an embodiment, the method may further comprise: generating, by the software creating program, a project schedule based at least in part on the project template, the project schedule including events related to the creation of the software program; and managing, by the software creating program, the events related to the creation of the software program. In an embodiment, the events related to the creation of the software program may include at least one of: a project milestone; a code commit; and a customer message. In an embodiment, the method may further comprise: passing, by the software creating program, at least one event ID to a communication program; and sending, by the communication program, a message to the customer based on the event ID. And in an embodiment, the method may further comprise: receiving, by a communication program, a message from the customer; and parsing, by the communication program, the received message into the software creating program. 

What is claimed is:
 1. A method for creating a custom software application, the method comprising: receiving, via an interactive interface, an input describing the custom software application, the input comprising at least a selection of a platform and a plurality of features associated with the custom software application; providing a code library comprising software code components comprising software code for creating different software applications; determining, by a software creating component based on the input, which software code components that already exists in the code library can be used to assemble the custom software application; determining, by the software creating component based on the input and based on the determined existing code components, new software code components that must be created that integrate with the determined existing code components to create the custom software application; and creating, via a project builder, a project outline for creating the custom software application, the project comprising at least a team for creating the custom software application and a project template.
 2. The method of claim 1, further comprising, by the project builder: assigning the determined existing code components to a new code library; and initiating transfer of the determined existing code components from the code library to the new code library.
 3. The method of claim 2, further comprising: receiving, from the team, one or more of the new software code components; and adding the one or more of the new software code components to the new code library.
 4. The method of claim 1, further comprising: matching, by a team selector component, one or more of the new software code components to the team member in a database including a plurality of team members, the team member having expertise for generating the one or more of the new software code components.
 5. The method of claim 4, wherein the matching further comprises matching a timing requirement received from the customer for creating the custom software application to an availability of the team member.
 6. The method of claim 4, wherein the matching further comprises further comprises matching a location requirement received from the customer for creating the custom software application to location of the team member.
 7. The method of claim 1, further comprising creating a project schedule for creating the custom software application.
 8. A method for creating a custom software application, the method comprising: receiving, via an interactive interface, an input describing the custom software application, the input comprising at least a selection of a platform and a plurality of features associated with the custom software application; providing a code library comprising software code components comprising software code for creating different software applications; determining, by a software creating component based on the input, which software code components that already exists in the code library can be used to assemble the custom software application; determining, by the software creating component based on the input and based on the determined existing code components, new software code components that must be created that integrate with the determined existing code components to create the custom software application; creating, via a project builder, a project outline for creating the custom software application, the project comprising at least a team for creating the custom software application and a project template; and generating a project schedule based at least in part on the project template, the project schedule including events related to the creation of the custom software application; and managing the events related to the creation of the customer software application.
 9. The method of claim 8, further comprising, by the project builder: assigning the determined existing code components to a new code library; and initiating transfer of the determined existing code components from the code library to the new code library.
 10. The method of claim 9, further comprising: receiving, from the team, one or more of the new software code components; and adding the one or more of the new software code components to the new code library.
 11. The method of claim 8, further comprising: matching, by a team selector component, one or more of the new software code components to the team member in a database including a plurality of team members, the team member having expertise for generating the one or more of the new software code components.
 12. The method of claim 11, wherein the matching further comprises matching a timing requirement received from the customer for creating the custom software application to an availability of the team member.
 13. The method of claim 11, wherein the matching further comprises further comprises matching a location requirement received from the customer for creating the custom software application to location of the team member.
 14. The method of claim 8, further comprising creating a project schedule for creating the custom software application.
 15. A method for creating a custom software application, the method comprising: receiving, via an interactive interface, an input describing the custom software application, the input comprising at least a selection of a platform and a plurality of features associated with the custom software application; providing a code library comprising software code components comprising software code for creating different software applications; determining, by a software creating component based on the input, which software code components that already exists in the code library can be used to assemble the custom software application; determining, by the software creating component based on the input and based on the determined existing code components, new software code components that must be created that integrate with the determined existing code components to create the custom software application; creating, via a project builder, a project outline for creating the custom software application, the project comprising at least a team for creating the custom software application and a project template; generating a project schedule based at least in part on the project template, the project schedule including events related to the creation of the custom software application; and managing the events related to the creation of the customer software application; and implementing an automated customer relationship management process that include an event manager that is configured to process events including project milestones, code commits, customer messages, and passes event IDs to appropriate sub-systems, and is further configured to implement a chatbot that is configured to send messages to customer based on event ID and parses inbound messaging into the event manager.
 16. The method of claim 15, further comprising, by the project builder: assigning the determined existing code components to a new code library; and initiating transfer of the determined existing code components from the code library to the new code library.
 17. The method of claim 16, further comprising: receiving, from the team, one or more of the new software code components; and adding the one or more of the new software code components to the new code library.
 18. The method of claim 15, further comprising: matching, by a team selector component, one or more of the new software code components to the team member in a database including a plurality of team members, the team member having expertise for generating the one or more of the new software code components.
 19. The method of claim 18, wherein the matching further comprises matching a timing requirement received from the customer for creating the custom software application to an availability of the team member.
 20. The method of claim 18, wherein the matching further comprises further comprises matching a location requirement received from the customer for creating the custom software application to location of the team member. 